home *** CD-ROM | disk | FTP | other *** search
- This directory contains small programs that demonstrate some basic
- features of the the ViewKit, displaying windows, handling command line
- options, interacting with the window manager, and so on. The examples
- are:
-
- generic
- =======
-
- The simplest possible ViewKit application. Just displays an empty
- window.
-
- generic2
- =========
-
- Extends the generic example by adding a menu pane to the window.
-
- run
- ====
-
- Demonstrates how to use VkApp::run to customize handling of the X event loop.
-
- pending
- ====
-
- Demonstrates how to use VkApp::handlePendingEvents to customize handling
- of the X event loop. This is much like "run".
-
- hello
- ======
-
- The basic "hello world" program, viewkit style. This example
- demonstrates subclassing from VkSimpleWindow.
-
-
- callback
- =========
-
- Demonstrates how to use Xt-style callbacks with ViewKit and C++.
-
-
- cmdline
- ========
-
- Show how to use the Xt-style command-line argument mechanism to set a
- resource from the command line.
-
-
- cmdline2
- ==========
-
- Extends the above example by retrieving the value of a resource and
- placing it in a class data member.
-
- busy
- =====
-
- Demonstrates the use of the "busy()" and "notBusy()" functions.
-
- stopwatch
- ==========
-
- A simple "stopwatch" program that demonstrates a more complex widget
- tree in a ViewKit window. This example also show some other viewkit
- facilties, including the VkPeriodic class, which provides a simple
- interface to XtAppAddTimeout, and also uses the XmGrid widget. This
- example also uses a viewkit-style C++ member function callback to
- interface with the timer.
-
- wmquit
- ======
-
- This demo puts up two windows. If you ask to close either one with
- the window menu, you are asking to close just that window. The demo
- puts up a confirming dialog for that window for you.
-
- If you click on the label of either window, then you are asking to close
- both widows (i.e. the whole application). What happens next depends on
- the setting of the resource "quitMode" (which defaults to "each").
-
- If this resource is "each", behavior is unchanged from the way this behaved
- in previous releases. The windows that are OK to close get closed, and any
- that are not OK remain open.
-
- If this resource is "all", the all windows get closed if all are OK to
- close. Otherwise no windows get closed.
-
- Note that this does not cover the case of a window manager quit, such as
- double-clicking on the window manager menu square. If the application
- wanted to handle this, it would need to override
- VkSimpleWindow::handleWmDeleteMessage() and/or
- VkSimpleWindow::handleWmQuitMessage().
-